Found in

• Nightly 112.0a1

Affected versions

• Nightly 112.0a1
• Firefox 110.0.1
• Firefox 111.0b7

Tested platforms

• Affected platforms: Windows 10, macOS 13, Ubuntu 22.04
• Unaffected platforms: none

Preconditions

• Install the Firefox en-CA build
  Set browser.search.region to CA in about:config
  Save 1 or 2 addresses in about:preferences#privacy, Forms & Autofill section
  One address to be written on multiple lines such as:
  10123
  S Sheridan
  Rd

Steps to reproduce

1. Go to https://www.newbalance.ca/
2. Add one item to cart and proceed to checkout
3. Use autofill feature to visualize the autofill dropdown, to preview the values and to autofill the Phone Number field
4. Click in any autofilled eligible field(e.g. First Name) and select the Clear Autofill form option from the dropdown menu
5. Click twice in any eligible field(e.g. First Name) and use the autofill option

Expected result

• Phone Number field is autofilled and the Phone number value is cleared after using the autofill and Clear Autofill form the second time.

Actual result
3.1. Clicking twice in the Phone Number field doesn't display the Autofill dropdown
4.1. The values from the Phone Number field are not cleared properly when using the option.
Value such as (6__) -_ is still displayed in the Phone Number field after using the Clear Autofill Form option.
5.1. Phone number field can no longer be autofilled after using the autofill feature the second time.
Value such as (6__) -_ is still displayed in the Phone number field.

Regression range

• Not a recent regression.

Additional notes

• In Google Chrome there is no Clear form option either for Phone number and the phone value is not cleared properly.
  However the autofill dropdown is displayed for the Phone Number field in Google Chrome and the autofill feature can be used multiple times to autofill this field.

:epopescu, if you think that's a regression, could you try to find a regression range using for example mozregression?

HI Ina, could you help verify whether this issue is fixed now? thank you!

(In reply to Dimi Lee [:dimi] from comment #4)

HI Ina, could you help verify whether this issue is fixed now? thank you!

The issue persists in the latest Nightly 115.0a1 (2023-05-23) on Windows 10 x61(+attachment)

This phone number field is not cleared properly is a site issue, we can also reproduce the same issue in Chrome.
I'll close this bug as fixed given that we can autofill the phone number field now

Hi Dimi,
The same behavior as in the description is still present in the latest Nightly 117.0a1. Clicking twice in the Phone Number field doesn't display the Autofill dropdown and the Phone Number field can no longer be autofilled after using the autofill feature the second time, after clearing the form.

(In reply to Alin Ilea, Desktop QA from comment #8)

Hi Dimi,
The same behavior as in the description is still present in the latest Nightly 117.0a1. Clicking twice in the Phone Number field doesn't display the Autofill dropdown and the Phone Number field can no longer be autofilled after using the autofill feature the second time, after clearing the form.

Hi Alin, Thank you for verifying this issue. Sorry I thought this issue was about "not showing autofill dropdown for phone number (before clearing form) AND various incorrect behavior after clearing form".

I was able to reproduce a similar issue on https://www.newbalance.co.uk as well on the latest nightly 138.0a1, on Win 10.
The Phone Number field does not get previewed or autofilled every time autofill is triggered from other fields. Additionally, when trying to autofill the form starting from the Phone Number field, the autofill dropdown does not appear. However, once the field is filled, the 'Clear Autofill Form' dropdown is displayed.
This happens regardless of the dynamic form support prefs and only for the phone field. Autofill and Clear work correctly for all the other fields.

The same issue reoccurs on https://www.newbalance.ca/ in the latest Nightly 138.0a1 where the autofill dropdown no longer appears in the Phone field after the value has been cleared at least once. This issue is not reproducible in Google Chrome.

This is caused by 1920036.